Skip to content

Add translation for OOP advanced files - #131

Open
lacatoire wants to merge 1 commit into
php:masterfrom
lacatoire:add-oop-advanced-translations
Open

Add translation for OOP advanced files#131
lacatoire wants to merge 1 commit into
php:masterfrom
lacatoire:add-oop-advanced-translations

Conversation

@lacatoire

Copy link
Copy Markdown
Member

Add Italian translation for anonymous classes, constructors/destructors, inheritance and static keyword

@lacatoire
lacatoire force-pushed the add-oop-advanced-translations branch from 477a7f9 to 56e6038 Compare February 26, 2026 17:06
@lacatoire lacatoire closed this May 10, 2026
@lacatoire lacatoire reopened this Jul 15, 2026

@vpinti vpinti left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a misalignment with the current English source.

anonymous.xml, decon.xml, and inheritance.xml were updated in en after this PR's declared revisions by commit dff848b1 (#5728, "Fix grammar in oop5"). Most of it is English-only grammar fixes that don't affect the translation, but the commit also converts a few <para> to <simpara>, which these files don't reflect yet. Those changes should be applied and the EN-Revision bumped to dff848b1:

  • anonymous.xml: d6f54016dff848b1
  • decon.xml: 82fc6a1cdff848b1
  • inheritance.xml: f94d9039dff848b1 (this file already reflects the later #5600 fix — the 'PHP is great.' output — while still declaring the earlier revision)

static.xml is fully aligned.

Comment thread language/oop5/decon.xml
</note>
<note>
<para>
Poiché le proprietà promosse vengono tradotte sia in una proprietà che in un parametro di funzione, qualsiasi

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Questa traduzione suona poco naturale in italiano:

  • "qualsiasi e tutte" è un calco di "any and all"; in italiano basta "tutte".
  • "per entrambe le proprietà e i parametri" rende "both... as well as" in modo ambiguo.

Suggerimento:

Poiché le proprietà promosse vengono convertite in una proprietà e in un parametro di funzione, si applicano tutte le restrizioni di denominazione valide per entrambi.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants